home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000255_misckit-reques…aska.et.byu.edu_Tue Sep 6 16:15:54 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
5KB
Return-Path: <misckit-request@alaska.et.byu.edu>
Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA01038; Tue, 6 Sep 94 16:15:41 -0600
Received: from YVAX2.BYU.EDU by alaska.et.byu.edu; Tue, 6 Sep 1994 16:14:54 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-9 #7277)
id <01HGSQOV2NHC9N52VJ@yvax.byu.edu>; Tue, 06 Sep 1994 16:14:21 -0600 (MDT)
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.3-9 #7277)
id <01HGSQOJX67K91WC3Y@yvax.byu.edu>; Tue, 06 Sep 1994 16:14:02 -0600 (MDT)
Received: from darth.byu.edu by alaska.et.byu.edu; Tue,
6 Sep 1994 16:09:22 -0600
Received: by darth.byu.edu (NX5.67d/NX3.0M) id AA01021; Tue,
6 Sep 94 16:10:01 -0600
Received: by NeXT.Mailer (1.100)
Received: by NeXT Mailer (1.100)
Date: Tue, 06 Sep 1994 16:10:01 -0600
From: Don Yacktman <don@darth.byu.edu>
Subject: Work in progress...
To: misckit@alaska.et.byu.edu
Reply-To: don@darth.byu.edu
Message-Id: <9409062210.AA01021@darth.byu.edu>
Content-Transfer-Encoding: 7BIT
Hi there everybody!
I've been (and am) busy at work on folding new submissions
and bug fixes into the MiscKit and I'm also improving things
a bit. I have quite a bit left to do, so it will take a little
while to get the next release out. Sorry about that, I do
appreciate the patience... if you've sent changes I should be
working on putting them into the kit. If you don't see them in the
next release _please_ re-send them to me and complain at me! :-)
One of the improvements that I'm working on is changing over
to PB project management for the library projects. (This is
done via the tool project and a hacked Makefile.[preamble/
postamble] and requires no modifications to PB itself.) In
the process of moving over, an issue has arisen and I'd like
some input.
Several times in the past we have brought up the possibility
of splitting the main library up into smaller libraries that
can be included as needed so that it is unnecessary to
include the whole big library. Right now we do have
MiscSwapKit and MiscInspectorKit libraries that are generated
in addition to the main library. But while I'm switching
over, it would be very easy to divide things up a bit more if
there is demand for it.
Reasons for doing this:
(1) You don't have to have code for objects you don't use
included in your app.
(2) Objects and categories that don't rely upon the AppKit
could be placed in a separate lib, thus allowing non-appkit
apps to use at least that much of the kit.
(3) It helps the organization be a bit more coherent.
...and more stuff someone will probably bring up...
Why you might not want to do this:
(1) You may have to include more than one library in your
project and have to know which libraries depend upon each
other so that you are sure you included all the parts
that you need.
(2) Any project using the MiscKit will need to have minor
changes made in the PB.project to handle the changes.
...and more stuff someone will probably bring up...
Note that when we get NS 4.0, we can do dynlibs, like a
shlib, so #1 of the plusses will become a moot point. The
MiscKit code wouldn't be in your app anyway in that case. Of
course, splitting up the kit would make some of the objects
more useful for non-NeXT Obj-C users. Again, that's a sort
of moot point, though, since the projects will be using PB
for maintenance meaning that non-NS users will need to have
their own Makefiles anyway and that means they could organize
the libs any way they like anyhow.
So, I lean toward breaking things up a bit--I still think it
would be worth the effort--but would like to hear everyone
else's thoughts on this. I think the majority would like to
see this happen, but I'd still like to hear feedback on this.
And, for those who like the idea, how should I split things
up? There have been two basic ideas on this. The first is
to go for dependencies to delineate organization: Make a lib
that depends on libsys_a and a second that requires the
appkit. Then non-appkit users use a part of the kit; appkit
users add in the second part for more functionality. The
other option is to delineate by function; this would parallel
what we already have with MiscInspectorKit and MiscSwapKit.
I like this method, but perhaps a mixing of the two divisions
would work best. Anyway, I'd like to hear how people would
like to see things split up.
I think it would be best to discuss this openly on the
misckit list so that everyone can respond and refine the
ideas until we arrive at a sort of consensus. I suspect that
suggestions made will often parallel how you _use_ the kit;
those who only use a part of the kit will probably suggest
placing that part into a library. (Like those who only use
MiscString.)
So, to summarize:
(1) do you want me to split things up more than they already are?
(2) if so, how do you think they ought to be split?
Followups to misckit@byu.edu please.
---
Later,
-Don Yacktman
Don_Yacktman@byu.edu